feat: expose Step Functions executions to automation - #368
Conversation
- Add a read-only failure-first execution JSON command and MCP tool. - Report the 200-execution cap and document the stable contract.
|
Warning Review limit reachedNext included review available in 8 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Repository: DevopsArtFactory/unic/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (9)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![amazon-q-developer[bot]](https://avatars.githubusercontent.com/in/1220912?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR successfully exposes Step Functions executions through the CLI and MCP interface with consistent patterns and comprehensive test coverage. The implementation follows existing conventions for resource queries, properly handles error cases, and includes appropriate pagination warnings. The failure-first triage ordering and 200-execution limit are clearly documented and tested.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
YoungJinJung
left a comment
YoungJinJung
left a comment
There was a problem hiding this comment.
Reviewed head f79d9cb. I read the complete nine-file diff, tests, issue context, CI, prior reviews, comments, and inline discussion. The bounded 200-execution query, stable failure-first ordering, conservative cap signal, UTC serialization, CLI/MCP wiring, permissions, and documentation are aligned; no actionable concerns remain. Local validation passed: make test, make build, schema inspection, and git diff --check. Approval and merge remain for an independent reviewer because this GitHub identity authored the PR.
youngjinjung-linq
left a comment
youngjinjung-linq
left a comment
There was a problem hiding this comment.
Reviewed head f79d9cb. I read the complete nine-file diff, tests, CI, issue context, prior reviews, comments, and inline discussion. The bounded Step Functions query, stable failure-first contract, conservative cap signal, UTC serialization, CLI/MCP wiring, permissions, and documentation are aligned; no actionable concerns remain. Local validation passed: targeted tests, make test, make build, schema inspection, and git diff --check.
# Conflicts: # README.md # docs/development.md # internal/cli/resources.go # internal/cli/resources_operations.go # internal/cli/resources_operations_test.go # internal/mcp/agent_surface_test.go # internal/mcp/server.go # internal/mcp/server_test.go # skills/unic-aws/SKILL.md
…ph (#378) Put Install Script before Homebrew under Installation. The Homebrew path needs three commands and a trust decision since Homebrew 6.0.0 (#369); the script is one line with no trust step, so it is the lower-friction entry point for a first-time reader. Both remain documented. This does not close #376 — that asks for one-command `brew install unic`, which is gated on homebrew-core notability — but it is the part available today. Also collapses the "The server provides the read-only resource operations listed above ..." paragraph, which appeared three times in a row with three different example-prompt lists. That was a regression from merging the #360 fills serially: #364, #367 and #368 each edited the sentence to name their own tool, and the conflict resolutions for #367 and #368 kept both sides rather than merging them. The surviving sentence names no example tool, since doing so is what made the line conflict on every fill and the command list above already enumerates them. The six distinct prompts are preserved. Closes #377 Co-authored-by: YoungJinJung <18644538+YoungJinJung@users.noreply.github.com>
2 participants
Summary
unic resources step-function-executions --state-machine <arn> --jsonusing the existing failure-first execution ordering.list_step_function_executionsover MCP with strict arguments andstates:ListExecutionsmetadata.Related Issues
Refs #360
Validation
go test ./internal/cli ./internal/mcp ./internal/services/aws -run "TestStepFunction|TestCatalogFeaturesHaveAgentSurfaceDecision|TestReadOnlyOperation|TestMCPCapabilities" -count=1make testmake buildgit diff --check./unic schema resources step-function-executions --jsonChecklist
docs/branch-naming-harness.mddocs/documentation-harness.md)docs/pages updated if architecture, auth, config, or workflow changed